The management packs for the connector services have been changed so that the discovery process for the Connector Service now occurs once every four hours. Any errors related to the Connector Service are not reported in Operations Manager until the discovery of the Connector Service object is complete. Additional connector services that you install high availability will not be monitored until the next scheduled discovery.

Workaround: If you need to run discovery immediately, stop and then restart the Health Service on the computer that is running the Connector Service. For example, you might want to run the discovery process after you install additional connector services for high availability.

The prerequisite check feature of connector installation fails if the check detects any previous versions.

Workaround: Use the Uninstall Program or the Add or Remove Programs feature in Windows to ensure that all previous versions of Operations Manager Interop Connectors are uninstalled. If they are not, uninstall all previous versions and components of Microsoft Interop Connectors from the management group in which you plan to install the connectors. Also uninstall Interop Provider and Interop Core components from the remote systems on which you plan to install the Interop Providers.

Any Windows-based server that hosts either Operations Manager 2007 R2 or the Interop Provider must have the English version of Microsoft Visual C++ 2008 Redistributable Package installed to allow correct installation and configuration of the components.

Workaround: For the English version of the Microsoft Visual C++ 2008 Redistributable Package download that is appropriate for your server type, see the information in the Microsoft Download Center (http://go.microsoft.com/fwlink/?LinkId=117778).

You can install the English version of the Microsoft Visual C++ 2008 Redistributable Package and another language version on the same computer.

If the SQL Server database instance that is to be used for the connector service database is installed on a clustered server running SQL Server, you must specify the database instance. For servers that are not clustered, selecting the SQL Server Database Instance field on the Connector Configuration database page of the connector service installation wizard is optional.

Workaround: When you install the connector service on clustered servers, in the SQL Server Database Instance text box on the Connector Configuration database page, enter the name of the database instance to be used. The SQL Database Name can remain as the default, SCInterop.

A user account with permissions to access the Administration pane in Operations Manager 2007 R2 might not have sufficient permissions to read or run stored procedures in the SCInterop database. The lack of permissions will prevent such a user account from accessing the Connectors Configuration UI in the Administration pane.

Workaround: The user account that is used to administer Operations Manager 2007 R2 must also have SQL DBO privileges on the SCInterop database. Typically, you use SQL Server Management Studio to grant permissions to a user account.

When a connector is installed and you access the Connectors set-up .msi file by clicking it or by using the Add or Remove Programs feature in Windows, the Change, repair, or remove installation page appears. The repair function for Connector installation is disabled. If you right-click the .msi file, you will see the Repair selection. If you click the Repair selection, you will receive an error message and the function will fail.

Workaround: To make a repair to a specific connector, uninstall that connector and reinstall it. For complete information on Connectors installation, see the Operations Manager 2007 R2 Connectors Deployment Guide.

When you configure a subscription by using the Product Connectors Subscription Wizard, it is best not to select to forward Closed alerts. Forwarding closed alerts can cause an unexpected amount of alerts to be forwarded. Because the Closed check box on the Criteria page of the Product Connectors Subscription Wizard might be selected by default, make sure that you clear the Closed check box.

When you configure Operations Manager 2007 R2 Connectors at installation, the OpsMgr Connector for <EMS> Connector Configuration dialog box appears. Use the <EMS> server name field to enter the name of the primary server for the remote system. However, this server name is not validated. To prevent forwarding operations from failing, make sure that you enter a valid name for the remote system server.

When you run the System Center Operations Manager 2007 R2 Connector to HP Operations Manager on a UNIX-based system, the Interop Provider (scxcimd) and the daemon (scinteropd) must be started in the same locale that HP Operations Manager is running. If the locales are not the same, the provider and scinteropd will fail to connect to HP Operations manager and “Invalid Login” will be logged in the log files.

Workaround: When you run the System Center Operations Manager 2007 R2 connector for HP Operation Manager on a UNIX-based system, the Interop Provider (scxcimd) and scinteropd daemon must be started in the same locale as HP Operations Manager is running under. If not, the provider and the daemon will fail to connect to the HP Operations Manager connector, and an 'Invalid Login' message will be logged in the scx log files.

For example, if the HP Operations Manager connector was started with a locale set to “ja_JP.SJIS” and the scxcimd daemon (Interop provider) was started with the locale set to “C”, an ’Invalid Login’ message would be logged in the scx log the first time we try to forward a new alert from System Center Operations Manager 2007 R2 to the HP Operations Manager connector.

If any text is non-English in any field settings for alerts that are forwarded by Operations Manager 2007 R2 Connectors, forwarding can fail or the data can become corrupted. Non-English data for alert text is not supported.

Workaround: Only use connectors to components that generate alerts in English.

When you include Product Knowledge or Context in a TEC alert, you must reduce the Maximum field size setting on the Operations Manager tab of the TEC Connector Configuration dialog box to a lower number, such as 1,000. If these field size settings exceed 1,000 bytes, one of the following scenarios could occur.

Scenario 1:

1. The alert is forwarded to TEC.
   
   
2. TEC receives the alert.
   
   
3. Because the alert is too large, it will not pass the TEC rules.
   
   
4. The alert eventually reaches a MAX Retries status.
   
   

Scenario 2:

1. The alert is forwarded to TEC
   
   
2. Because the alert is too large, it is dropped and therefore, it is not created in TEC.
   
   
3. The alert eventually reaches a MAX Retries status.
   
   

To determine whether the alert size is the cause of a forwarding failure, do the following:

1. On the TEC server, use the Tivoli command, wtdumprl, to determine whether the alert was received and processed. If the alert is too large, the TEC server might have dropped it.
   
   

If the event was created in TEC, but the alert TicketID property was never updated with the TEC event ID, do the following:

• Examine the tec_rule file for an error that is similar to the following: Apr  8 17:41:11.326091 tec_rule[421948] ERR tec_msg.c:130: Packet size too small to contain message
  
  

The tec_rule file is in the /tmp directory on UNIX-based systems and in the /$DBDIR/tmp directory on Windows-based computers.

1. Open the TEC Connector Configuration dialog box.

2. Select the Operations Manager tab.

3. Set the Maximum field size to 1,000 or less.

If the TEC Connector Service is not configured with the correct port number, the service will not be able to communicate with TEC and it will generate errors.

Workaround: When you forward alerts to a TEC server that is running Windows, you must set the TEC server port on the Connector Configuration UI to the specific port on which TEC is listening. The connector is set up to work with UNIX-based servers or with TEC servers that use the UNIX Port Mapper to determine TEC’s port. A TEC server that is running Windows uses a hard coded port which is set, by default, to 5529. You must set the TEC server port to the specific port on which TEC is listening and then restart the Connector Service.

On rare occasions the Operations Manager SDK will produce an ‘Unknown Error’ message. When this occurs, the connector service will stop. You can check the connector service logs to see whether there is more information about why the connector service was stopped. To recover, restart the connector service.

Installation of Operations Manager 2007 R2 Connectors sometimes fails with a warning that the product is already configured.

Workaround:

For Windows Server 2008-based servers, delete the following files:

• C:\ProgramData\TECConfigInstall.xml\
  
  
• C:\ProgramData\REMEDYConfigInstall.xml\
  
  
• C:ProgramData\OVOConfigInstall.xml\ or C:ProgramData\UNVConfigInstall.xml\
  
  

For Windows Server 2003-based servers, delete the following files:

• C:\Documents and Settings\All Users\Application Data\TECConfigInstal.xml\
  
  
• C:\Documents and Settings\All Users\Application Data\REMEDYConfigInstal.xml\
  
  
• C:\Documents and Settings\All Users\Application Data\OVOConfigInstal.xml\ or C:\Documents and Settings\All Users\Application Data\UNVConfigInstal.xml
  
  

When you install the Operations Manager 2007 R2 Connectors components on a Windows Server 2008-based computer by using a domain user account, the installation can fail even though the account has the appropriate permissions.

Workaround: Use the following procedure to perform the installation.

1. On the Start menu, right-click Command Prompt, and then click Run as administrator.

2. In the Command window, change to the location of the installation file.

3. Run the msiexec /i command by using the appropriate Connector set-up file, for example:

   msiexec /i SciConnectorSetup_x86.msi

It is recommended that you install the connector service and the Interop Provider Component on different servers.

The Connector Service does not have to be installed on a server with the Operations Manager agent. If the Connector Service is installed on a server that does not have the Operations Manager agent installed, errors and events related to connectors will not be raised in the console, and the management pack will not discover the connector.

You must authenticate certificate verification before you set up High Availability and add systems in the EMS Communication Order dialog of the connector properties.

When you set up the second server, manually run the scicert utility to pull back the certificate on the provider system and create the trusted relationship between the second connector service system and the provider system.

To view scicert usage information, for your specific configurations, open a command window, type scicert, and then press ENTER.

Operations Manager 200 R2 connectors should only be installed on English language–based versions of operating systems.

If you install the connector service on the same server on which your SQL Server database is installed, and then you restart the server, it is probable that the connector service will attempt to start before SQL Server has started. This leads to the connector service failing to start. If this scenario occurs, you can manually restart the connector service after SQL Server is running.

To prevent the scenario from happening, you can use Service Manager to add a recovery action to the service.

1. From Control Panel, select Administrative Tools, and then select Services.

2. In the right pane of the Services window, right-click the OpsMgr Connector for <EMS> entry, and then select Properties.

3. In the Properties dialog box, select the Recovery tab.

4. In the First failure list, the Second failure list, and Subsequent failures list, select Restart the Service.

5. In the Restart service after field, enter 1, and then click OK.

6. Close Services close Administrative Tools, and then close Control Panel.

When you install a connector and specify a Windows-based server for the Interop Provider, the certificate that is generated on the Provider server is based on the name of the server and not on the fully qualified domain name (FQDN) of the server. Do not specify FDQN in the <EMS> Provider field of the Connector Configuration wizard. Instead, use the name of the server that the Interop Provider is installed on.

The account that you use when you set up the connector service must have “Login as Service” privileges.

Installing multiple providers on the same server is not supported in this release of Operations Manager 2007 R2 Connectors.

To send non-English data to Remedy, the (local) non-English version of the Remedy User tool must be installed on the provider server. The non-Unicode applications locale setting must also be set to the same non-English locale. For example, if you use Japanese data, you must install the Japanese User tool, and, in Windows, you must set the locale for non-Unicode applications to Japanese.

In addition, when you install the AR Server, you must set the DATA language to the local (non-English) language. The DATA language can be set only when the AR Server is installed. It cannot be changed after installation.

The “opsmgr” account can be used only by the connector service. If you use the “opsmgr” account to update tickets, the updates will not be sent back to Operations Manager 2007 R2.

Be aware that Connector and Provider installation opens ports 1433 and 1270. Port 1433 is the default SQL Server port. Port 1270 is the WS-Man port.

If you are using the TEC Connector to forward alerts to a Windows-based TEC Server, you will need to set the TEC Server Port on the Connector Configuration UI to the specific port to which TEC is listening.

The connector is set up to work with UNIX-based and Linux-based Windows-based TEC Servers which use the UNIX Port Mapper to determine the TEC port. TEC on Windows uses a hard coded port. By default, this is set to 5529. You will need to set the TEC Server Port to the specific port on which TEC is listening and then restart the connector service. Otherwise the connector service will be unable to communicate with TEC and will generate errors.